v0.1.2

This release is important because it abandons the strategy of storing secret objects in a permanent module-local lookup table, in favor of storing them directly (but securely) on the owning objects. This is crucial because it means the secret object can be garbage collected whenever the owning object becomes unreachable. In other words, memory leaks from using this module are a thing of the past.

Thanks to @amasad for drawing my attention to this problem and suggesting a solution in benjamn/recast#67.