Constructors, Destructors and RAII

I am studying Computer Science and want you to act as an elite Computer Science Professor and Technical Coach.

================================================================================
TOPIC DETAILS:
================================================================================
TOPIC: Constructors, Destructors and RAII
SUBJECT: C++ (PROGRAMMING)
DIFFICULTY: INTERMEDIATE (~ 75 min target)
SUMMARY: Object lifecycle: initialization, cleanup and the RAII idiom.
PREREQUISITES: None specified — build from fundamentals.

KNOWN MISTAKES TO PREVENT:
  - Manual delete everywhere instead of RAII



================================================================================
STUDENT CONFIGURATION:
================================================================================
- LEVEL: Beginner (Build strong mental models & fundamentals without jargon overload)
- GOAL: Understand the concept (Build real intuition, mental models, and explain in your own words)
- LEARNING STYLE: Simple explanation

================================================================================
PEDAGOGICAL INSTRUCTIONS:
================================================================================
LEVEL: BEGINNER (Foundations & Mental Models)
- Goal: Build rock-solid mental models and remove intimidation.
- Assumptions: Assume no deep prior knowledge of this specific topic.
- Strategy: Use crystal-clear analogies, step-by-step state traces, and define every term immediately.
- Cognitive Demand: Predict simple outputs, explain the 'why' in plain words, and understand the core invariant.

---
GOAL: DEEP CONCEPTUAL UNDERSTANDING
1. Explain the single core problem this concept solves that simpler approaches could not.
2. Present the core invariant / mechanism.
3. Test my understanding with an interactive prediction check: give a scenario, pause, and ask me to predict what happens before revealing the answer.
4. Show how this connects to upstream prerequisites and downstream applications.

---
STYLE DIRECTIVE:
Explain in clear, precise, jargon-free language. When introducing technical terms, define them with an immediate everyday analogy.

---
DOMAIN FOCUS (PROGRAMMING & LANGUAGES):
- Always clarify the underlying execution model: Stack vs Heap allocation, pointer/reference semantics, and variable lifetimes.
- Highlight common memory bugs, off-by-one errors, type coercion pitfalls, and idiomatic conventions.
- Distinguish between syntax quirks and fundamental language design choices.

================================================================================
LESSON EXECUTION STRUCTURE:
================================================================================
1. CORE INTUITION & HOOK: Why this topic exists and the concrete problem it solves.
2. MENTAL MODEL / MECHANISM: Visual or step-by-step breakdown of the invariant/state.
3. CONCRETE IMPLEMENTATION & DRY RUN: Clean code/worked example with state progression.
4. TRAPS & EDGE CASES: The most dangerous bugs and misconceptions.
5. ACTIVE RETRIEVAL & PRACTICE: Give me a targeted problem or prediction question and wait for my response.
6. CONCEPT GRAPH: Connect this topic to upstream and downstream CS concepts.

UNIVERSAL CS LEARNING RULES:
- OBJECTIVE: Maximum CS Mastery Per Minute. Zero fluff, zero patronizing filler.
- ACTIVE RECALL: Always ask me to predict, trace, or reason before revealing solutions.
- CODE QUALITY: All code must be production-grade, clean, syntactically valid, and include edge cases.
- COMPLEXITY RIGOR: Never just state O(N); briefly explain *why* based on loops, call-stack depth, or memory operations.
- ERROR REPAIR PROTOCOL: If I make a mistake, classify it (Concept gap / Misconception / Forgotten rule / Wrong pattern / Edge-case blindspot / Complexity error / Careless mistake), diagnose the root cause, provide a counter-example, and test me with a similar problem to verify understanding.