You can hide compiler warnings by adding some key words to your class.
Ok, there are very few situations when you would want to do this. Some argue that it should never be done and no code should have warnings. However, if you are really sure then you can use the following.
In my example I have a class that overrides the Equals method but not the GetHashCode method. There is no way of returning a correct hash code in this situation and overriding it and calling the base would suggest the class takes responsibility for that being correct.
So the compiler throws up this warning:
warning CS0659: SPListItemChange' overrides Object.Equals(object o) but does not override Object.GetHashCode()
Fair enough.
In my class definition I can add the following:
#pragma warning disable 0659 //override Equals but not GetHashCode
public class SPListItemChange
{
A short compile later 0 warnings.