Too many sprites?

[Nexus]

Wasn't error-proneness one of the reasons to avoid raw arrays? So why replace them with something that's only slightly less so?

It's not slightly less, it's far less. Computing indexes is easy. Implementing memory management, an STL interface and value semantics isn't. And one can still encapsulate the computation of indexes to make it trivial.

But anyway, we're comparing different things. For two-dimensional automatic arrays, the equivalent is a nested std::array, not std::vector.

I'd rather use boost::multi_array or something similar instead of a vector with manually recalculated indices.

boost::multi_array is buggy, on MSVC++ 2010 some operations don't even compile.

By the way, why did you change your name?

[Silvah]

Computing indexes is easy. Implementing memory management, an STL interface and value semantics isn't.

Yet the latter is easier for me, because I never can get the former right. I just don't remember what is multiplied by what.

boost::multi_array is buggy, on MSVC++ 2010 some operations don't even compile.

Then fix it (you'll make the world a better place! ), or use different library - I explicitly said "or something similar", didn't I?

By the way, why did you change your name?

Since I'm playing the devil's advocate here quite often, I changed it to something that better reflects the reality

[Vovosunt]

Unless you actually have 10500 DIFFERENT sprites I wouldn't do that.
You should make a tiles array/map only with the tiles that are different, then draw those tiles by moving and then rendering, not by actually making lots of sprites.

I have 7500 tiles and I'm only using 24 sprites