As far as I know, there is no way to scope SurpressWarning to the method declaration only.
This leaves you with these possibilities:
- Increase the visibility of the method to package or protected. Slightly increasing visibility has the added benefit that it becomes available to unit tests.
- Create a dummy method which has call to the unused methods. (This feels really ugly).