Terminar a lo bruto con un thread

[[escafandra]]

La API TerminateThread:

BOOL TerminateThread(
    HANDLE hThread,    // handle to the thread 
    DWORD dwExitCode     // exit code for the thread 
   );

La he probado y funciona. Lo he hecho de esta manera:

bool __fastcall MyThread::Exit()
{
   DWORD ExitCode;
   bool R = GetExitCodeThread((HANDLE)Handle, &ExitCode); 
   if(R){
      TerminateThread((HANDLE)Handle, ExitCode);
   } 
   return R;    
}

El problema está en la advertencia que hace Microshoft y algunos foros, sobre la peligrosidad de usarla, y recomiendan terminar de forma más controlada:

TerminateThread is used to cause a thread to exit. When this occurs, the target thread has no chance to execute any user-mode code. DLLs attached to the thread are not notified that the thread is terminating. The system frees the thread's initial stack.

Windows Server 2003 and Windows XP/2000: The target thread's initial stack is not freed, causing a resource leak.

TerminateThread is a dangerous function that should only be used in the most extreme cases. You should call TerminateThread only if you know exactly what the target thread is doing, and you control all of the code that the target thread could possibly be running at the time of the termination. For example, TerminateThread can result in the following problems:

* If the target thread owns a critical section, the critical section will not be released.
* If the target thread is allocating memory from the heap, the heap lock will not be released.
* If the target thread is executing certain kernel32 calls when it is terminated, the kernel32 state for the thread's process could be inconsistent.
* If the target thread is manipulating the global state of a shared DLL, the state of the DLL could be destroyed, affecting other users of the DLL.

A thread cannot protect itself against TerminateThread, other than by controlling access to its handles. The thread handle returned by the CreateThread and CreateProcess functions has THREAD_TERMINATE access, so any caller holding one of these handles can terminate your thread.

If the target thread is the last thread of a process when this function is called, the thread's process is also terminated.

The state of the thread object becomes signaled, releasing any other threads that had been waiting for the thread to terminate. The thread's termination status changes from STILL_ACTIVE to the value of the dwExitCode parameter.

Terminating a thread does not necessarily remove the thread object from the system. A thread object is deleted when the last thread handle is closed.

Otra Cita: Why you should never call Suspend/TerminateThread

No se si terminando como he expuesto mas arriba, puedo tener problemas mas adelante en el transcurso de la aplicación. Las pruebas que he realizado han sido satisfactorias, no he tenido problemas, pero tras la advertencia, dudo, y no se si es necesario tomar alguna medida adicional.

Saludos.