Challenge 2: Two Genuinely Different Process() Implementations — Possible Solution
====================================================================

Program.cs:

interface IPrintable { void Process(); }
interface ISavable { void Process(); }

class Document : IPrintable, ISavable
{
    void IPrintable.Process() => Console.WriteLine("Printing the document...");
    void ISavable.Process() => Console.WriteLine("Saving the document to disk...");
}

Document doc = new Document();
((IPrintable)doc).Process();
((ISavable)doc).Process();

Output:

    Printing the document...
    Saving the document to disk...

Explanation:
Both IPrintable and ISavable declare a method with the identical name
and signature, Process(). Ordinarily this would be a real naming
collision -- in java1-6's Java, the only way to satisfy both
interfaces would be for a single Process() method to serve both
purposes, or for one interface to be renamed. Explicit interface
implementation sidesteps this entirely: each Process() is written as
InterfaceName.Process(), tying it permanently to that specific
interface, so the SAME Document instance genuinely has two distinct
behaviors, selected purely by which interface type the reference is
cast to.

WHY THIS WORKS AS AN ANSWER
------------------------------
This builds the exact IPrintable/ISavable name-collision scenario the
chapter uses, with two genuinely different method bodies coexisting
on one class -- demonstrating the capability the chapter names as
having no Java equivalent at all.