Andre Kostur wrote in message...
>
> Keep in mind that std::vector has to do (Well, is very likely to do)
> dynamic memory to store its contents. Arrays do not. You might try
> std::tr1:array instead...

A valid argument. But, sticking 2+ meg in the stack might be a source of his
problem (stack overflow/corruption?).
And if you 'new' the arrays, well, I think std::vector is a good choice.

[ I don't know how C++ sets up the stack, but in assembler, it was precious
realestate. My logic is small things on stack, big things in dynamic(heap).
Feel free to inform/correct me on this point. :-}]
--
Bob R
POVrookie