Clarify MFC operator overrides impact on ASan

Author: zacklj89

docs/sanitizers/asan-known-issues.md

@@ -59,7 +59,7 @@ int main() {
 
 AddressSanitizer (ASan) uses a custom version of `operator new` and `operator delete` to find allocation errors like [`alloc_dealloc_mismatch`](error-alloc-dealloc-mismatch.md). Running the linker with [`/INFERASANLIBS`](../build/reference/inferasanlibs.md) ensures that ASan's `new`/`delete` override has low precedence, so that the linker chooses any `operator new` or `operator delete` overrides in other libraries over ASan's custom versions. When this happens, ASan may not be able to catch some errors that rely on its custom `operator new` and `operator delete`.
 
-[MFC](../mfc/mfc-concepts.md) includes custom overrides for `operator new` and `operator delete`. Any operation that utilizes these provided operators instead of the ASan provided `operator new` and `operator delete` might miss errors entirely or classify them incorrectly as a result:
+[MFC](../mfc/mfc-concepts.md) includes custom overrides for `operator new` and `operator delete`. When `MFC` overrides are used instead of the ASan provided `operator new` and `operator delete`, ASan might miss errors entirely or classify them incorrectly as a result. The following errors may be missed or incorrectly classified:
  - [`alloc_dealloc_mismatch`](error-alloc-dealloc-mismatch.md)
  - [`double-free`](error-double-free.md)
  - [`heap-use-after-free`](error-heap-use-after-free.md)