In the mid-term, “code contracts” (in 4.0) will be a better answer to this. They are available now (with academic or commercial licences), but will be more integrated in VS2010. This can provide both static analysis and runtime support.
(edit) example:
Contract.RequiresAlways( x != null );
Simple as that… the code contracts engine works at the IL level, so it can analyse that and throw warnings/errors from calling code during build, or at runtime. For backwards compatibility, if you have existing validation code, you can just tell it where the sanity checking ends, and it’ll do the rest:
if ( x == null ) throw new ArgumentNullException("x");
Contract.EndContractBlock();