Breaking API change.

[QAston]

Regardless of the number of people using dmocks it's probably nice to warn about future breaking changes to the API.

Due to it's current way of handling errors dmocks has problems with mocking nothrow methods. Right now expectation exceptions are thrown while methods are replayed - this doesn't play well with nothrow. My plan is to make expectation validation happen on Mocker.verify (as it probably should be in the first place) - therefore for future compatibility you should call Mocker.verify when you expect expectation exceptions.

[QAston]

It turns out I can avoid the issue by adding a simple, backward compatibile switch. Sorry for the inconvenience.