Most of the cases, I hate ToolTips.

Especially this kind;

So, I wrote a simple remedy.

How to Use:

When mouse goes into the danger zone, it moves out from there instantly and automatically.

Danger Zone:

Codes:

CoordMode, Mouse, Screen
noMouseZone()
OnMessage(0xFF, "noMouseZoneSetting")
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
noMouseZone()
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
{
    VarSetCapacity(_, 8 + A_PtrSize)
    NumPut(1, _, 0, "UShort")
    NumPut(2, _, 2, "UShort")
    NumPut(0x00000100, _, 4)
    NumPut(A_scriptHWND, _, 8)
    DllCall("RegisterRawInputDevices", "Ptr", &_, "UInt", 1, "UInt", 8 + A_PtrSize)
}
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
noMouseZoneSetting( )
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
{
    DllCall("GetRawInputData", "UInt",, "UInt", 0x10000003, "Ptr", 0, "UInt *", _, "UInt", 8 + A_PtrSize * 2)
    VarSetCapacity(@, _)
    DllCall("GetRawInputData", "UInt",, "UInt", 0x10000003, "Ptr", &@, "UInt *", _, "UInt", 8 + A_PtrSize * 2)
    MouseGetPos, mouseX, mouseY

    ; X From 950 To 1041 meanValue is 995....  From 950 To 995 goes to 1042....  From 995 To 1041 goes to 949
    ; Y From 420 To 1020

    IfWinActive, SDL Trados
    {
        ToolTip % mouseX ", " mouseY "`n"
        If (420 < mouseY && mouseY < 1020)
        {
            If( 950 < mouseX && mouseX < 995 )
            {
                MouseMove, 1042, mouseY
                SoundBeep, 2222,44
            }
            If( 995 < mouseX && mouseX < 1041)
            {
                MouseMove, 949, mouseY
                SoundBeep, 1111, 44
            }
         }
     }
     ToolTip
}

Modify the figures for your environments.

This is just a brief testing. 
I hope some smart one show me a better idea.  

Enjoy..