>>It is the case. The Remove() method is not tied to one instance, but exists on every instance,
>>and can be used on any of them. Until then it is "the function to remove a member object from
>>a collection."
>
>But it is tied to one instance - *the* instance that invokes it.


At the time of writing / reading the documentation that's not known. In code you provide both variables, the collection instance, and the object instance to remove, at runtime. But prior to that, and from a documentation point of view, it is the function which exists to operate upon any collection to remove any object within that collection, hence "a collection" and "an object".