It's worth noting that N is N expectations on `nil` and not all the expectations (because of the conditional) and the existing implementation resets N times anyway, this just resets properly when you use `allow_message_expectations_on_nil`.

It can't hurt to refactor it now I guess, but I'm not sure how to remove the state, as the point is you have to call `allow_message_expectations_on_nil` to enable the feature for the duration of the example, so you have to reset it before the next example. Unless we move that method onto one of the instance classes...