manual memory management

[Joseph Rushton Wakeling]

On 01/08/2013 10:43 PM, Jonathan M Davis wrote:
> std.container.Array and built-in arrays are _very_ different. Array is a
> container, not a range. You can slice it to get a range and operate on that,
> but it's not a range itself.

Is there a particular reason why Array can't have a range interface itself?

> On the other hand, built-in arrays aren't true containers. They don't own or
> manage their own memory in any way, shape, or form, and they're ranges.

Forgive the naive question, but what _is_ the definition of a 'true container'? 
  Is managing its own memory a necessary component?  Or just for D's concept of 
a container?