Document memory problem on iOS version as well (ref: #299/#308)

README.md

@@ -68,7 +68,7 @@ License for iOS version: MIT only
 - Triggers have only been tested on iOS, known to be broken on Android (in case [Android-sqlite-connector](/~https://github.com/liteglue/Android-sqlite-connector) is disabled) and Amazon Fire-OS.
 - INSERT statement that affects multiple rows (due to SELECT cause or using triggers, for example) does not report proper rowsAffected on Android (in case [Android-sqlite-connector](/~https://github.com/liteglue/Android-sqlite-connector) is disabled) or Amazon Fire-OS.
 - On Windows "Universal" (8.1), rowsAffected can be wrong when there are multiple levels of nesting of INSERT statements.
-- Memory issue observed when adding a large number of records on Android and Amazon Fire-OS, due to JSON implementation (ref: [#18](/~https://github.com/litehelpers/Cordova-sqlite-storage/issues/18))
+- Memory issue observed when adding a very large number of records (due to JSON implementation) on Android, Amazon Fire-OS (ref: [#18](/~https://github.com/litehelpers/Cordova-sqlite-storage/issues/18)), and iOS (ref: [#299](/~https://github.com/litehelpers/Cordova-sqlite-storage/issues/299) and [#308](/~https://github.com/litehelpers/Cordova-sqlite-storage/issues/308))
 - A stability issue was reported on the iOS version when in use together with [SockJS](http://sockjs.org/) client such as [pusher-js](/~https://github.com/pusher/pusher-js) at the same time (see [#196](/~https://github.com/litehelpers/Cordova-sqlite-storage/issues/196)). The workaround is to call sqlite functions and [SockJS](http://sockjs.org/) client functions in separate ticks (using setTimeout with 0 timeout).
 - If a sql statement fails for which there is no error handler or the error handler does not return `false` to signal transaction recovery, the plugin fires the remaining sql callbacks before aborting the transaction.
 - DROP table does not actually delete it in WP(7/8) version, due to limitations of CSharp-SQLite.