Prevent parameters verification for a method that should never be called

Hi!

There is a bug when we add a parameter constraint on a method that should never be called.
I know, that seems to be a weird test case.
But I have this kind of code in a generic mock generator.

I mainly propose a test case that show you the bug.
I also propose a fix, inspired by the fix for the "any invocation" case. 
I needed to add a getter method on the InvokedCount class, so there could be a better solution.

Cheers,
Thomas.