Minor fix: using self instead of non-volatile copy
- Not a bug, since control wasn't returned to the caller yet, but bad form to break implicit 'one volatile read' rule.
- TECHNICALLY copy could have triggered a change in the items. If someone had actually done that they *deserved* what they got.
Merge branch 'master' of github.com:Strilanc/ObjC-CollapsingFutures