What I'm saying is this: say we have a method that is not annotated with any `@Inject`. Then we find that an ancestor has `@javax.inject.Inject`. Well then this is the warning that we're testing for.

 But I don't stop there and give a match right away. Instead, I continue checking the ancestors and look for a Guice Inject on a higher up ancestor. Now, the child method will get injecr since `@com.google.inject.Inject` is inherited. So this is only a warning and not an error (and the warning will be caught in the GuiceOverridesGuiceInjectableMethod matcher).

In all likelihood this strange pattern will never come up. But I did it this way as I think it's technically correct if it does as it won't give a duplicate error.