Reserve_ids documentation has a typo, and implementation seems bugged #37

I've omitted all the usual fields because I feel they are irrelevant, I hope that is okay. Please refer to the PR here: #36

One basic issue is that the documentation of reserve_ids doesn't match the the typespec. The other issue is that the documentation overall is ambiguous enough that I'm actually not sure of its behavior. I would expect it to sequentially reserve all IDs starting from the provided complete key, up to a count of "num", but since all it passes to the underlying API is [complete_key] * num I'm actually not positive that that's what it's doing, or even what it's exactly doing, without anything further to refer to.