Added a Verify build configuration,

althought currently, it's a copy of the Release configuration, and has the
same settings.
Added a Code Analysis rule set, and turned it on

in the Verify build configuration. The rule set contains all rules, except
for

CA1006	Do not nest generic types in member signatures
CA2210	Assemblies should have valid strong names

CA1006 I always turn off, because I consider it hypocritical (Microsoft
itself nests generics, e.g. in System.Linq.Expressions), and also because
I consider the motivation for the rule (that nested generics are difficult
to understand) dated.

CA2210 is turned off in order to enable all developers to build without
warnings. Before releasing a version of Exude, we will sign the assembly
with a strong name, but since the strong name key file shouldn't be
included in a publicly available source control repository, this rule is
turned off in order to avoid build errors for developers without access to
the strong name key file.

The Code Analysis rule set still treat warnings as warnings. When all
warnings have been addressed, Code Alaysis warnings should be treated as
errors.

The build-release scripts don't build in Verify mode yet.
Executed Verify build from BuildRelease

build scripts. Currently, this causes build warnings to appear, because
there are Code Analysis warnings in the build output.
Marked Exude as CLS Compliant,

which also caused me to change the name of the TestMethod property to
HostTestMethod, becuase it isn't CLS Compliant to have a two public
members that only differ in case (there's an underlying protected field
called 'testMethod').
Added a custom Code Analysis dictionary.
Addressed Code Analysis warning CA1018

(http://msdn.microsoft.com/en-us/library/ms182158.aspx).
Adressed a Code Analysis warning

by explicitly supplying a format provider to string.Format.
Suppressed a Code Analysis warning.

The Justification attribute provides an explanation.
Turned all potential Code Analysis warnings into

errors, which is OK now, because there are no Code Analysis errors.