AssertCount still asserts in a release about morelinq HOT 2 CLOSED

We could have VerifyCount for checks that should remain in Release builds and 
AssertCount for the Debug-only builds.

The name borrows from debug assertion by-design. Usually, no one expect LINQ
operators to go mute, silent or disappear from code between debug and release 
builds
because LINQ operators form part of a result-producing chain and the chain 
should not
be broken. As a result, "assert" here is used to indicate that an exception 
will be
thrown on failure to meet the condition. AssertCount is not designed for 
internal
sanity check but for actual run-time assertion.