Codegen causes ilverify errors - Callvirt on a value type method.

[KevinRansom]

The ilverifier baseline file has exemptions for :

[IL]: Error [CallVirtOnValueType]: : FSharp.Compiler.Text.RangeModule+comparer@548::System.Collections.Generic.IEquality
Comparer<FSharp.Compiler.Text.Range>.GetHashCode([FSharp.Compiler.Service]FSharp.Compiler.Text.Range)][offset
0x00000002] Callvirt on a value type method.
[IL]: Error [CallVirtOnValueType]: : FSharp.Compiler.Text.RangeModule+comparer@546::System.Collections.Generic.IEquality
Comparer<FSharp.Compiler.Text.Range>.GetHashCode([FSharp.Compiler.Service]FSharp.Compiler.Text.Range)][offset
0x00000002] Callvirt on a value type method.

We should modify our codegen to produce as few errors as possible when running

[vzarytovskii]

Famous last words - this one should be a really easy fix, we have one (?) place when we decide call vs callvirt, it should be a matter of adding another check (if it's the method of obj called on the valuetype).

Should also consider the following suggestion from the docs:

When calling methods of System.Object on value types, consider using the constrained prefix with the callvirt instruction. This removes the need to emit different IL depending on whether or not the value type overrides the method, avoiding a potential versioning problem. Consider using the constrained prefix when invoking interface methods on value types, since the value type method implementing the interface method can be changed using a MethodImpl. These issues are described in more detail in the Constrained opcode.