Jim - no problem
I think you are correct, it is the word "array" that can cause confusion; in it's purest form an array is as you say, merely a block of memory whereas what we are all really wanting is a simple implementation of a "collection" or "list" which internally is an array with built-in intelligence for want of a better term. In my original post I actually used the word "collection" in brackets to suggest this was what I meant.
In my opinion, AppGameKit should remain primarily procedural with perhaps "object capabilities" in the future, a bit like PHP is now; i.e. you can develop using procedural code but you can build and think using objects if you want/need to.
Wrappers in some cases are good but as I'm sure you'll know, there are many issues with wrappers such as multiple/changing implementations, standards (or lack thereof), the compiler can't easily optimise them (if at all), general performance...etc.
For simple things like what we are discussing here, it would be nice if they were part of the core language.