Yes it has the capability built-in:
PS> Get-Process
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
102 3 11092 9044 45 1324 audiodg
762 8 1728 3560 77 624 csrss
639 12 4332 9676 159 688 csrss
132 5 2968 6156 75 0.95 2800 DPAgnt
206 12 15528 11912 110 736 DpHost
190 8 107700 68304 231 416.89 3924 dwm
495 10 22628 9156 139 3.66 3920 EDICT
68 3 1400 3692 52 1.03 4060 ehmsas
95 4 1752 2564 72 0.36 2592 ehtray
634 26 28896 33932 215 1,081.88 4004 explorer
541 22 90640 71584 287 125.86 2920 FeedDemon
91 3 1784 5052 65 1.75 4824 FlashUtil9e
43 2 1084 2876 52 0.09 3424 hpwuSchd2
0 0 0 12 0 0 Idle
426 11 9180 12828 118 10.13 3056 ieuser
1000 40 153556 126384 430 914.27 5576 iexplore
182 7 5932 8264 100 38.30 2780 ipoint
...
and try this to get all the DLLs for a specific process:
PS> Get-Process PowerShell | Select ProcessName -Expand Modules
Size(K) ModuleName FileName
------- ---------- --------
340 powershell.exe C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe
1180 ntdll.dll C:\Windows\system32\ntdll.dll
876 kernel32.dll C:\Windows\system32\kernel32.dll
792 ADVAPI32.dll C:\Windows\system32\ADVAPI32.dll
780 RPCRT4.dll C:\Windows\system32\RPCRT4.dll
...
--
Keith