Update to reflect reworked implementation.

asio/src/doc/overview/allocation.qbk

diff --git a/asio/src/doc/overview/allocation.qbk b/asio/src/doc/overview/allocation.qbk
index 59a708a..d071d52 100644
--- a/asio/src/doc/overview/allocation.qbk
+++ b/asio/src/doc/overview/allocation.qbk
@@ -51,12 +51,7 @@
 Custom memory allocation support is currently implemented for all asynchronous
 operations with the following exceptions:
 
-* `ip::basic_resolver::async_resolve()` on all platforms.
-
-* `basic_socket::async_connect()` on Windows.
-
-* Any operation involving `null_buffers()` on Windows, other than an
-  asynchronous read performed on a stream-oriented socket.
+* Asynchronous SSL operations.
 
 [heading See Also]
 

asio/src/doc/overview/threads.qbk

diff --git a/asio/src/doc/overview/threads.qbk b/asio/src/doc/overview/threads.qbk
index d005c0e..475a7aa 100644
--- a/asio/src/doc/overview/threads.qbk
+++ b/asio/src/doc/overview/threads.qbk
@@ -35,16 +35,6 @@
 
 * must block all signals.
 
-[note The implementation currently violates the first of these rules for the
-following functions:
-
-[mdash] `ip::basic_resolver::async_resolve()` on all platforms.
-
-[mdash] `basic_socket::async_connect()` on Windows.
-
-[mdash] Any operation involving `null_buffers()` on Windows, other than an
-asynchronous read performed on a stream-oriented socket.]
-
 This approach is complemented by the following guarantee:
 
 * Asynchronous completion handlers will only be called from threads that are