- Milestone: 2.0 --> 3.0
Add a event pool type having a fixed, non-dynamic event pool. Currently the only pool type is dynamic and grows if needed. The caching pool can host at max CACH_SIZE number of reusable events. If one more event is released to the pool it will not be cached by deleted. In the same way, requesting a new event (by calling generate()) from an empty pool will allocate a new event. Thus, the pool acts more like a resource/event buffer. The purpose of such caching pool is to keep memory requirements a bit more restricted. The size of the dynamic event pool will only increase in order to match the worst case scenario - thus wasting memory. A cahcing pool will restrict memory consumption at the potential cost of performance (alloc/free events when cache is empty/full).