C++: Rename PointerWrapAround to PointerOverflow

Overflow was the terminology I found for this in the C standard (C11
6.5.6-8).

cpp/ql/src/Likely Bugs/Memory Management/PointerOverflow.qhelp

@@ -38,7 +38,7 @@ checking if adding it to <code>ptr</code> creates a pointer so large that it
 overflows and wraps around.
 </p>
 
-<sample src="PointerWrapAround-bad.cpp" />
+<sample src="PointerOverflow-bad.cpp" />
 
 <p>
 In both of these checks, the operations are performed in the wrong order.
@@ -60,7 +60,7 @@ allocation.
 The next example shows how to portably check whether a number is outside the
 range of an allocation between <code>ptr</code> and <code>ptr_end</code>.
 </p>
-<sample src="PointerWrapAround-good.cpp" />
+<sample src="PointerOverflow-good.cpp" />
 </example>
 <references>
 <li><a href="https://blog.regehr.org/archives/1395">Pointer Overflow Checking [Embedded in Academia]</a></li>

cpp/ql/src/Likely Bugs/Memory Management/PointerOverflow.ql

@@ -1,12 +1,11 @@
 /**
- * @name Reliance on pointer wrap-around
+ * @name Range check relying on pointer overflow
- * @description Adding a value to a pointer
+ * @description Adding a value to a pointer to see if it overflows relies
- *              to see if it "wraps around" is dangerous because it relies
  *              on undefined behavior and may lead to memory corruption.
  * @kind problem
  * @problem.severity error
  * @precision high
- * @id cpp/pointer-wrap-around
+ * @id cpp/pointer-overflow
  * @tags reliability
  *       security
  */

cpp/ql/test/query-tests/Likely Bugs/Memory Management/PointerOverflow/PointerOverflow.qlref

@@ -0,0 +1 @@
+Likely Bugs/Memory Management/PointerOverflow.ql

cpp/ql/test/query-tests/Likely Bugs/Memory Management/PointerOverflowCheck/PointerWrapAround.qlref

@@ -1 +0,0 @@
-Likely Bugs/Memory Management/PointerWrapAround.ql