>>But it is tied to one instance - *the* instance that invokes it.
>
>But in the context there is no definite instance of a collection. If there were, we would know it's name or location in the code, but we don't.

For me the difference in wording is based on the different type concepts of .Net and vfp: in .Net description there is no definate instance, but a number of possible collection classes, as they need to be and are typed: Collection(Of T).RemoveAt. With vfp you have just one (base)class for all collections handling any type of loadable item, even if you may subclass it.

Dunno iv Viv was aiming at that as well with:

>>'a' would only seem correct to me if (in .NET) there was a static method of the Collection type. e.g.:

Collection.Remove(collection,,element)