Exit and destructor of C + +

Almost every textbook is written in this way, and when a class is instantiated, the constructor is bound to execute, and the destructor is bound to execute when the class is freed. It seems to be in people's minds that constructors and destructors, like twins, perform constructors and are bound to perform destructors ...

Today, I did an experiment to completely overturn the theory. The code is as follows:

#include "stdafx.h"
using namespace std;
class mycs
{
　public:
　　mycs()
　　{
　　　cout<<"构造函数"<<endl;
　　　exit(1);
　　}
　　~mycs()
　　{
　　　cout<<"析构函数"<<endl;
　　}
};
mycs cs;
int _tmain(int argc, _TCHAR* argv[])
{
return 0;
}

The Exit function is executed in the constructor, so the destructor must not be executed. But this exit is placed elsewhere, and destructors are executed. I guess the reasons are as follows:

Because exit has a higher priority than the destructor, exit automatically returns the permission to the OS after it has been executed ... That's it......