New Tiled Data Manager ideas and tests

[Schleimer, Ben]

> 
> functionality? That's
> why i like this idea! Simple reading/writing i too easy job
> for two cores and they are stuck in the bottleneck - shared
> memory controller. But scaling and other stuff... they are
> good pretenders for TileProcessors. But first i should solve
> problems with object-oriented stuff (constructors, etc.)
> that takes about 20% of time.

You'll get a massive speedup if you override new/delete for KisTileData and use a pool allocator. Also you KisTileData::m_data should be pool allocated as well.

Cheers
Ben