Nope, no issue.  There was another place using @YES; I just wanted to add a test for using a constant in an OCMockValue and this was the only other place andReturnValue which was easy to change to test the new macro.  It may be better to make a separate test case using an NSRect (maybe just use the new test with the other pull request, which does use NSZeroRect) and abort this change.