Add validation against unintended invocations to mocked types/instances from inside an expectation/verification block

[rliesenfeld]

Sometimes a user will write a "result = new SomeClass(someMock)" recording, where the called constructor happens to make calls on "someMock". Such indirect recordings are unintended, and can result in confusing exceptions.

Such misuses of the mocking API should be detected, with a helpful exception message shown.