Add paging support to calls that implement start/count #4

From Raymond Yee:

One of the things that I was looking for in your library was how you handled paging of results. I see that you allow people to pass in start, count parameters. I was wondering whether you have given thought to trying to making results available as iterators in which you've hidden the process of paging from a developer using your library. In other words, I can just ask your library for say all the albums in my collection, one at a time, until there are no more albums -- and your library would handle calling the API enough times to get me all the results. Does that make sense?

Link