complier will define a default empty destructor and inline it. I am only aware of 3 cases where an empty destructor absolutely has to be defined.
- virtual destructor in base class (not in any derived) (Eclipse can spot that)
- class has a member that is incomplete (forward declaration) (compiler error)
- class defined in Windows .dll that uses different C++ runtime than .exe (hours of fun!)

If you absolutely want to see an empty destructor I will (re)define it albeit inline.