I propose to drop those two methods for a couple of reasons:

1. They confuse a lot of people
2. Only affect the expectation and not the subject
3. They only affect the top-level members of an object. As soon as BeEquivalentTo goes one level deeper, it will fall-back to the run-time types.

If somebody really wants to include or exclude certain members, they can either use an anonymous type as the expectation or use one of the other APIs to include or exclude certain members.

Also may affect #1860