SATransactionalOperation => SASyncTransactionalOperation
Generic SAOperationsPool
Transactional operation is not synchronous now, no semaphores
Both non-sync transactional and cascade operations work inside each other (no semaphores)
Better OperationsPool
adds passing results beetween operations (now 1 arg only)
Passing multiple results beetween operations
bump to 0.0.7
podspec
transactional operations run inside cascade operations may pass results too
bump to 0.0.8
bump to 0.0.9
Numerous fixes and improvements

- More careful properties and ivars handling
- AsyncOperations registered in OperationsPool when run inside transactional context
syncOperation and asyncOperation: running in specific queues with c functions helpers
async operations inside transactional operation: running in specific queues
synchronize OperationsPool instance, not class + using queue instead of @synchronized
cleanups
Cleanups, fixes, more tests

- Correct removal of operations from pool
- Tests for transactional operation with results
bump to 0.0.10
defaultQueue() and friends

- adds defaultQueue() and setDefaultQueue()
- atomic operations inside cascade are run inside defaultQueue() if it is set
- axes syncTransactionalOperation method of SACascadeOperation class