Actually, I don't think that test should pass...

If I want to be sure that no constructor arguments were misspelled, the correct way to do that would be to invoke `Verify(ConstructorInfo)`.

It's entirely expected for an `IdiomaticAssertion` that there are many paths that generally are no-ops, because the passed in parameter doesn't fit the scenario that this assertion attempts to capture.