Memory Peak during removeExpiredObjects #102

Memory can peak very high in removeExpiredObjects (which might lead to crashes), caused by the for-loop which accesses all elements inside the cache. This could be easily fixed by wrapping the code after the for-loop inside an autoreleasepool.