clarification on "Limitations and caveats"

[justinmk]

Is the Limitations and caveats section of the readme outdated?

The current implementation caches this information in a ConcurrentDictionary object. The objects it stores are never flushed.

8ed5f61 added automatic GC.

If you are generating SQL strings on the fly without using parameters it is possible you will hit memory issues.

Does 8747316 have implications for that statement?

[NickCraver]

Yes, 8747316 added back unbounded implications, but since we don't track a hit count there cleanup isn't so easy. @mgravell think this is an issue?