Setup gets included in Verify despite being "unreachable"

[stakx]

Reproduction code:

public interface IX
{
    IX X { get; }
}

var mock = new Mock<IX>();
mock.Setup(m => m.X.X).Verifiable("1");
mock.Setup(m => m.X).Verifiable("2");
_ = mock.Object.X;

mock.Verify();

Actual behavior:

Verify throws a MockException with message:

The following setups on mock 'Mock<IX:00000002>' were not matched:
1: IX m => m.X.X

Expected behavior:

No exception should be thrown, since setup 2 overrides the "root" of setup 1 (m.X) and there's no longer any way of getting at 2's m.X.X through mock (on which verification is triggered).

[stakx]

Another similar case:

var mock = new Mock<IX> { DefaultValue = DefaultValue.Mock };
mock.SetupAllProperties();
(mock.Object.X).Setup(m => m.X).Verifiable();
mock.Object.X = null;

mock.Verify();

In the above example, the mock associated with the initial value of mock.Object.X keeps being tracked even though it becomes unreachable later when mock.Object.X is reset.