`EqualityComparer<object>.Default()` will be slow, will fall back to
`object.Equals()` which may do the right thing, the wrong thing, or be
useless due to using reference equality semantics.
In practice in this call site it likely doesn't matter anyway but I'd
rather be future-proof than not.