#17 Wrong error message about changed method signature

[CapnNemo]

Further to ID: 1373831, Clirr reports an error if a method is dropped in favour of a super-class implementation, and a new method added with a similar signature.

Rather than checking for a super-implementation, it seems to check for signature changes first.

One way round this is to keep the overloaded method, but just delegate to the parent.

The overloaded method can be dropped in the next version, and Clirr does not then complain.