[util.smartptr.shared.cast] Properly describe possibility of double deletion in notes (#7037)

Author: zhihaoy

source/memory.tex

@@ -4356,7 +4356,7 @@
 \begin{note}
 The seemingly equivalent expression
 \tcode{shared_ptr<T>(static_cast<T*>(r.get()))}
-will eventually result in undefined behavior, attempting to delete the
+can result in undefined behavior, attempting to delete the
 same object twice.
 \end{note}
 \end{itemdescr}
@@ -4393,7 +4393,7 @@
 \pnum
 \begin{note}
 The seemingly equivalent expression
-\tcode{shared_ptr<T>(dynamic_cast<T*>(r.get()))} will eventually result in
+\tcode{shared_ptr<T>(dynamic_cast<T*>(r.get()))} can result in
 undefined behavior, attempting to delete the same object twice.
 \end{note}
 \end{itemdescr}
@@ -4422,7 +4422,7 @@
 \pnum
 \begin{note}
 The seemingly equivalent expression
-\tcode{shared_ptr<T>(const_cast<T*>(r.get()))} will eventually result in
+\tcode{shared_ptr<T>(const_cast<T*>(r.get()))} can result in
 undefined behavior, attempting to delete the same object twice.
 \end{note}
 \end{itemdescr}
@@ -4451,7 +4451,7 @@
 \pnum
 \begin{note}
 The seemingly equivalent expression
-\tcode{shared_ptr<T>(reinterpret_cast<T*>(r.get()))} will eventually result in
+\tcode{shared_ptr<T>(reinterpret_cast<T*>(r.get()))} can result in
 undefined behavior, attempting to delete the same object twice.
 \end{note}
 \end{itemdescr}