Update README.md

Author: Roberto De Ioris

README.md

@@ -808,15 +808,9 @@ Memory management
 
 Dealing with 2 different GC's is really challenging.
 
-PyActor, PyPawn and PythonComponent automatically DECREF's the mapped classes. This should be enough unless you hold references
-in the python modules themselves. As this would be a bad programming practice, the current approach should be safe enough.
+Starting from release 20180226 a new memory management system has been added (FUnrealEnginePythonHouseKeeper, available here https://github.com/20tab/UnrealEnginePython/blob/master/Source/UnrealEnginePython/Public/PythonHouseKeeper.h). This new system is completely integrated with the Unreal Engine reflection-based GC and will hold track of each ue_PyUObject abd the related UObject to understand when a python object can be safely destroyed.
 
-In addition to this, every time a uobject has to return its UObject mapping, it checks for its validity and safety:
-
-```c
-#define ue_py_check(py_u) if (!py_u->ue_object || !py_u->ue_object->IsValidLowLevel() || py_u->ue_object->IsPendingKillOrUnreachable())\
-							return PyErr_Format(PyExc_Exception, "PyUObject is in invalid state")
-```
+The same system works for delegates, as well as Slate.
 
 
 Unit Testing