Is implementing RAII via constructors and destructors considered bad 'Modern C++'?

Question

With the advent of smart pointer in C++, is manually implementing RAII via constructors and destructors considered bad 'modern C++' practice? Or are there applications where this is still relevant?

Answer 1

Memory, via allocation, isn't the only kind of Resource that can be Acquired, so pointers aren't the only kind of beast that RAII is for.

Consider, for instance, a scoped lock:

template <class Lockable>
class lock_guard {
    Lockable& lck;
public:
    lock_guard(Lockable& lck)
        : lck(lck)
    {
        lck.lock();
    }

    ~lock_guard()
    {
        lck.unlock()
    }
};

No pointers. Still RAII. Still shiny, modern, and super useful.