Isolate.Verify.WasNotCalled() bugged in 6.1.2 - repro inside

In Isolator 6.1.2, given an empty A() in DLL A and an empty B() in DLL B, with both A() and B() faked, calling A() then asserting B() was not called results in an exception on account of Isolator believing incorrectly that B() was called.

The repro, bug highlighted:

[ img ]

When empty A() is not called, Isolator believes correctly that B() was not called:

[ img ]

Further data on this bug:

[ img ]

This appears to be the same bug as the one reported in thread "Method Not Called But Verify Says Unexpectedly Called" http://forums.typemock.com/viewtopic.php?t=1933

Hanukkah wish list: A fix for this bug and Isolator++ 64-bit.

Thanks!
Neil