Fixed an issue when, if expectationOrderMatters is YES, then the andForwardToRealObject would make expectations look out of order

Let's say you have a partial mock and do this:
[partialMock setExpectationOrderMatters:YES]
[[[partialMock expect] andForwardToRealObject] method1]
[[[partialMock expect] andForwardToRealObject] method2]

If method1 internally calls method2 and you call method1, then the mock will throw an exception. This is because the code that forwards the invocation to the real object happens before the code that checks to see if the expectation order is correct when doing setExpectationOrderMatters:YES