On top what other experts have mentioned already I would like to suggest an idea;

Since you implementing wrapper functions you could also handle the really generic and ugly errors like

when a user was trying to

Enumerable.Remove 999

and 999 was an index out of bounds you could take a better care of that with some sort of error handler? Perhaps a MsgBox with an actual explanation on the reason why something is not possible instead of that ugly general invalid procedure call or argument?

On top what other experts have mentioned already I would like to suggest an idea;

Since you implementing wrapper functions you could also handle the really generic and ugly errors like

when a user was trying to

Enumerable.Remove 999

and 999 was an index out of bounds you could take a better care of that with some sort of error handler? Perhaps a MsgBox with an actual explanation on the reason why something is not possible instead of that ugly general invalid procedure call or argument?

Also:

In the static Range() you should at least check that the endValue > startValue, and Repeat() the times > 1

Also, I am not sure if that's a good practice or not but when I am doing a library with static functions I prefer to Dim i as Long only once as a private global and then don't have to worry to dim it each time I need to loop using an i iterator.