clarify scope of sized dealloc mismatch detection

README.md

@@ -169,8 +169,9 @@ was a bit less important and if a core goal was finding latent bugs.
 * Fully out-of-line metadata
 * Deterministic detection of any invalid free (unallocated, unaligned, etc.)
     * Validation of the size passed for C++14 sized deallocation by `delete`
-      (detects type confusion if the size is different) and various containers
-      using the allocator API directly
+      even for code compiled with earlier standards (detects type confusion if
+      the size is different) and by various containers using the allocator API
+      directly
 * Isolated memory region for slab allocations
     * Divided up into isolated inner regions for each size class
         * High entropy random base for each size class region